With the shipment of Frontier Runtime, it's becoming more commonplace for script writers to need to be able to export Install files so they can easily be imported into Runtime.root. Included in this package are two desktop scripts that reduce the complexity of exporting Install files from your Frontier object database.
The exportInstallFile script exports an install file for a single application; the exportAllInstallFiles script exports the Install files for all apps that have tables in your system.verbs.apps table. Each install file contains the table of glue scripts for the application and the application's shared menu bar if it has one.
The exportInstallFile script prompts you for the name of the application whose Install file you want to export. Enter the name exactly as you would if you were calling one of the app's verbs. Then a dialog appears asking where you want the install file saved. Enter a name and select a folder. The install file is exported.
Note: in either of the two scripts, if the app doesn't have an "appInfo" sub-table, the script cannot export the install file. The appInfo table is automatically created by the Commercial Developers suite. If you must export the Install file for this app, and it doesn't contain an appInfo table, either contact the developer of the app, or use the Commercial suite to properly initialize the table.
The exportAllInstallFiles script does absolutely no prompting. It creates a folder named "Frontier Install Files" in the folder that the script was launched from. Then it loops over all apps in your system.verbs.apps table, exporting an Install file for each one. But stay by your computer. If this script encounters an app that doesn't have an appInfo table, it will tell you so in a modal dialog box. The standard "DDE" app table doesn't have an appInfo table. If you want to move that table from your Frontier.root to a Runtime.root, you need to do it with copy and paste.
